Prevent Dependabot workflows for private mirrors#8576
Prevent Dependabot workflows for private mirrors#8576desrosj wants to merge 1 commit intoWordPress:trunkfrom
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Test using WordPress PlaygroundThe changes in this pull request can previewed and tested using a WordPress Playground instance. WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser. Some things to be aware of
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. |
Currently, the
ifconditionals for workflows use one of two approaches to limit when they run: Run if the repository isWordPress/wordpress-developOR if the workflow is triggered by apull_requestevent. This prevents workflows from running needlessly on forks and mirrors when branches are synced or updated through push events, but still allows contributors to open PRs back to their forks to test changes before submitting them back.This can cause some issues with Dependabot, though. Dependabot is disabled by default for all forks. However, it is impossible to disable Dependabot for mirrors when a
dependabot.ymlfile is present. This is especially problematic for private mirrors, which consume resources for organizations.This switches the OR condition to run workflows if triggered by a
pull_requestAND the actor is not dependabot to prevent these workflows from running in this situation.Trac ticket: https://core.trac.wordpress.org/ticket/62221
This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.